@aaronstuder said:

@scottalanmiller Didn't Red Hat take Centos back in house?

That's a weird way to say it. "Back" would imply that they used to be in house. CentOS was a third party and Red Hat bought them.

@scottalanmiller said in Building ELK on CentOS 7:

@dafyre said in Building ELK on CentOS 7:

So... I went through and ran the script and it seems to have worked fine... What next?

Edit: To collect logs from the local server, I also had to install filebeat on this server. So I reckon I can now go and install it on all my other systems as well.

Yes, install Filebeat and point it to ELK. Check my Filebeat article for more info.

Didn't realize you had one. 8-) But I'm good now. Logs are collecting as we speak. Bonus: Fail2Ban and Apache logs also work great in ELK.

@ou_snaaksie said in Installing Rocket.Chat on CentOS 7:

The installation worked perfetly, but after restarting the server I am unable to access Rocketchat.

I've run the line:
/opt/Rocket.Chat/node_modules/forever/bin/forever start /opt/Rocket.Chat/main.js

but it is still not working.

Use this command to see what is listening...

netstat -tulpn

@scottalanmiller said in Installing MongoDB 3.2 on CentOS 7:

Just tested and deployed to CentOS 7.2 on Linode.

This failed me, so I went to the mongo docs and the baseurl contains the variable $releasever.

using that results in redhat//mongodb in the file, which is why I assume you hard coded that bit.

Escaping the $ fixes it.

cat > /etc/yum.repos.d/mongodb-org-3.2.repo <<EOF [mongodb-org-3.2] name=MongoDB Repository baseurl=https://repo.mongodb.org/yum/redhat/\$releasever/mongodb-org/3.2/x86_64/ gpgcheck=1 enabled=1 gpgkey=https://www.mongodb.org/static/pgp/server-3.2.asc EOF

@stacksofplates

Btw Centos got updated to:

CentOS 7.4 (1708)
CentOS Linux release 7.4.1708 (Core)

https://wiki.centos.org/Manuals/ReleaseNotes/CentOS7?action=show&redirect=Manuals%2FReleaseNotes%2FCentOS7.1708

Noteable mentions

At least 1024 MB RAM is required to install and use CentOS-7 (1708). When using the Live ISOs for install, 1024 MB RAM produces very slow results and even some install failures. At least 1344 MB RAM is recommend for LiveGNOME or LiveKDE installs.

The initramfs files are now significantly bigger than in CentOS-7 (1503). You may want to consider lowering installonly_limit in /etc/yum.conf to reduce the number of installed kernels if your /boot partition is smaller than 400MB. New installations should consider using 1GB, which is now the upstream recommended, as the size of the /boot partition.

Sadly Centos 7.4 does not work with this guide 😞 Damn

@dafyre said:

@scottalanmiller What separates the two? er... What makes Webmin not enterprise friendly vs Cockpit? (it has been a LONG time since I've used webmin and I haven't used Cockpit yet).

Webmin is a "third party unsupported add on crutch." It's whole purpose is to make UNIX graphical without using the officially supported toolsets. While that in and off itself isn't "bad", it's bad conceptually. It's purpose is to be a crutch for people who won't learn how to run the system and ends up being just like FreeNAS or whatever - just limitations and risk layered on top of the OS.

Cockpit is different. It is part of the OS itself, not an add on. It's fully managed and supported by the team that makes the OS (Red Hat, in this case.) In this way it is like the Microsoft GUI interface - still not ideal as a management tool, but stable and supported.

That Webmin is a huge, dangerous catch all for management and Cockpit is a limited graphical view of capacity planning with a few very simplistic management tools also makes them very different. Cockpit is not meant to replace being a good admin, it's meant to give some graphical views where they make sense. Webmin is meant to let people run an OS that they don't understand.

So I decided to try hooking up a new install of openfire to my domain controller (Zentyal). Turns out you need a more recent version of prototype.js to make it work correctly.

cd /opt/openfire/plugins/admin/webapp/js; mv prototype.js prototype.js.old; wget https://ajax.googleapis.com/ajax/libs/prototype/1.7.1.0/prototype.js systemctl restart openfire

At that point clear your browser cache if you had started the setup configuration via web browser already, and you should be able to complete the setup using your Active Directory information.

I know, I know, way beyond the article scope, but I figured it would save some of us a little headache.

@scottalanmiller I almost never use them. A few service accounts and that's about it.

@antonit said:

What is the default db admin?

root

@scottalanmiller said in Linux: The Lay of the Land and the Filesystem Hierarchy Standard:

@BRRABill said in Linux: The Lay of the Land and the Filesystem Hierarchy Standard:

So to wrap this question up...

Anything to be shared with users not on the local machine should be stored in /var and probably /var/exports

So a file structure such as

/var/exports/HRdata
/var/exports/XObackups
/var/exports/userhomefolders
/var/exports/sharedDOCS

Would be what you are expecting to see on a Linux file server....?

Yes, that would be a very good approach.

Thanks!

Hope it was a good question.

Had a spare laptop laying around. Installing CentOS now. Also planning on installing NextCloud here soon as well. Creating a repository/shared calendar for the family with this machine.

Updated as I figured out where things have moved away from the documentation that I had. The five minute install video is for Stacki 1.x and they have changed quite a bit at the core so that is why the video does not reflect the needs of the current installer. Avoid the StackiQ video for installation.

For those stumbling in here down the road, the current consensus is that FreePBX is the better option for your new PBX. Elastix 4 did release, but is not being updated enough to remain a contender at this point.

No, there is nothing like that. The filesystem is just not there. It would warn you, though, so you would know not to be trying to save to something that doesn't exist.

@JaredBusch said:

@coliver said:

@JaredBusch said:

Disabke SELinux and see if it works. Then if so, add the port as allowed to SELinux?

Looks like it was SELinux, setting it to permissive allowed the port to be used. Now to figure out how to allow the port in SELinux.

semanage port -m -t http_port_t -p tcp 82

That did it thanks.

To enable all yum operations to use a proxy server, specify the proxy server details in /etc/yum.conf. The proxy setting must specify the proxy server as a complete URL, including the TCP port number. If your proxy server requires a username and password, specify these by adding proxy_username and proxy_password settings.

The settings below enable yum to use the proxy server mycache.mydomain.com, connecting to port 3128, with the username yum-user and the password qwerty.

# The proxy server - proxy server:port number proxy=http://mycache.mydomain.com:3128 # The account details for yum connections proxy_username=yum-user proxy_password=qwerty

@DustinB3403 said:

Did you not have somewhere to jump off of?

XS/XO/XOA is all great, but seriously the thread count is stupid. The knowledge is lost in all the noise.

Original post has been updated to reflect the latest 0.9 release of the Minecraft Server.

@clisting said in Installing PocketMine MineCraft PE Server on CentOS 7:

it constantly disconnects me. the server appears to be online please help me.

I've not touched this in three and a half years, I'm afraid. This stuff easily doesn't work any longer 😞

@scottalanmiller said:

Nothing scarier than things that fix themselves 😞

Seriously upset about this. I will be rebooting the machine a few times today trying to make it do it again.